Skip to content

Conversation

@ShahzaibIbrahim
Copy link
Contributor

Having the scale factor being based on the screen DPI leads to unexpected result e.g. Image too big/small. Having a screen dpi independent factor leads to consistent results

@ShahzaibIbrahim ShahzaibIbrahim linked an issue Dec 10, 2025 that may be closed by this pull request
1 task
@github-actions
Copy link
Contributor

github-actions bot commented Dec 10, 2025

Test Results

  176 files  ±0    176 suites  ±0   25m 12s ⏱️ - 2m 0s
4 671 tests ±0  4 649 ✅ ±0  22 💤 ±0  0 ❌ ±0 
  482 runs  ±0    476 ✅ ±0   6 💤 ±0  0 ❌ ±0 

Results for commit 6c9e11e. ± Comparison against base commit f005865.

♻️ This comment has been updated with latest results.

Having the scale factor being based on the screen DPI leads to
unexpected result e.g. Image too big/small. Having a screen dpi
independent factor leads to consistent results
Copy link
Contributor

@akoch-yatta akoch-yatta left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, small adjustments to get rid of Display#getDPI calls that do not provide proper values on windows with monitor specific scaling enabled

@akoch-yatta akoch-yatta merged commit 9740516 into eclipse-platform:master Dec 15, 2025
23 checks passed
@akoch-yatta akoch-yatta deleted the master-224-snippets branch December 15, 2025 08:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Mark Device::getDPI() method as deprecated

2 participants